Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1699

reference: 660-tree-1
name: 1699
tree-preservation-order: undefined
660-tpo-1
uprn
address-text
point: POINT (-1.007112 50.863184)
geometry: MULTIPOLYGON (((-1.007055 50.863178,-1.007058 50.863189,-1.007066 50.863199,-1.007078 50.863208,-1.007094 50.863213,-1.007111 50.863215,-1.007129 50.863213,-1.007145 50.863208,-1.007158 50.863200,-1.007166 50.863190,-1.007169 50.863179,-1.007166 50.863168,-1.007159 50.863158,-1.007146 50.863150,-1.007130 50.863145,-1.007113 50.863143,-1.007095 50.863144,-1.007079 50.863149,-1.007067 50.863157,-1.007058 50.863167,-1.007055 50.863178)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL